Last updated: 2022-10-03

Checks: 6 1

Knit directory: factor_analysis/

This reproducible R Markdown analysis was created with workflowr (version 1.7.0). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.

R Markdown file: uncommitted changes

The R Markdown file has unstaged changes. To know which version of the R Markdown file created these results, you’ll want to first commit it to the Git repo. If you’re still working on the analysis, you can ignore this warning. When you’re finished, you can run wflow_publish to commit the R Markdown file and build the HTML.

Environment: empty

Great job! The global environment was empty. Objects defined in the global environment can affect the analysis in your R Markdown file in unknown ways. For reproduciblity it’s best to always run the code in an empty environment.

Seed: set.seed(20200623)

The command set.seed(20200623) was run prior to running the code in the R Markdown file. Setting a seed ensures that any results that rely on randomness, e.g. subsampling or permutations, are reproducible.

Session information: recorded

Great job! Recording the operating system, R version, and package versions is critical for reproducibility.

Cache: none

Nice! There were no cached chunks for this analysis, so you can be confident that you successfully produced the results during this run.

File paths: relative

Great job! Using relative paths to the files within your workflowr project makes it easier to run your code on other machines.

Repository version: 3ae2a1e

Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility.

The results in this page were generated with repository version 3ae2a1e. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.

Note that you need to be careful to ensure that all relevant files for the analysis have been committed to Git prior to generating the results (you can use wflow_publish or wflow_git_commit). workflowr only checks the R Markdown file, but you know if there are other scripts or data files that it depends on. Below is the status of the Git repository when the results were generated:


Ignored files:
    Ignored:    .RData
    Ignored:    .Rhistory
    Ignored:    analysis/.Rhistory
    Ignored:    output/.Rhistory

Unstaged changes:
    Modified:   analysis/ECT_2peer.Rmd

Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.

These are the previous versions of the repository in which changes were made to the R Markdown (analysis/ECT_2peer.Rmd) and HTML (docs/ECT_2peer.html) files. If you’ve configured a remote Git repository (see ?wflow_git_remote), click on the hyperlinks in the table below to view the files as they were in that past version.

File	Version	Author	Date	Message
Rmd	92eba45	XSun	2022-10-03	update
html	92eba45	XSun	2022-10-03	update

Introduction

Workflow:

Association test: factor ~ snp + covariates
For the pairs have multiple snps passing FDR < 0.2, do ECT

Results

The number of SNPs passing FDR < 0.2 in association tests

Version	Author	Date
92eba45	XSun	2022-10-03

ECT results

If we compute ECT FDR using all pairs have >= 3SNPs passing association FDR < 0.2 as before, no pairs will have ECT FDR <=0.2.

If we just use the pairs have >=15 SNPs, we can find some pairs pass the ECT FDR cutoff.

Results for all pairs have >=3SNPs

Version	Author	Date
92eba45	XSun	2022-10-03

Version	Author	Date
92eba45	XSun	2022-10-03

Results for all pairs have >=15SNPs

Version	Author	Date
92eba45	XSun	2022-10-03